Over 1,000 Windows 95 Programs/Over 1000 Windows 95 Programs (Microforum) (Disc 1).iso/1263/problems.doc

Text File | 1997-04-18 | 7.3 KB | 190 lines

         PROBLEMS.DOC

         KNOWN PROBLEMS AND BUGS

         This  document describes  known problems  and  bugs of  the SXT
         programs. They  have been found during testing or were reported
         by  users. I  provide this list  for informational  purposes so
         that every  user can have a look at the problems he/she may run
         into (but hopefully does not). This list may probably influence
         your decision, either positive or negative, whether to register
         or  not, but I  think everybody  should know  about before what
         he/she will get.

         For  additional  information  and  more  general questions  you
         should  also   look  at  the  chapters  'PROGRAM  LIMITATIONS',
         'TROUBLE SHOOTING' and 'FREQUENTLY ASKED QUESTIONS' in SXT.DOC.

         If a  real bug is reported I will try to  fix it if this can be
         done  with reasonable  effort, but  I  cannot give  a guarantee
         (Remember:  I do all these things in  my free time, this is not
         the job I earn my money!).  I can do a fix only if I am able to
         reproduce the bug, therefore it is necessary to provide example
         code (as  small as possible, concentrated on the problem) which
         causes  the error.  If possible, the  memory address  where the
         error  occurred would be very helpful.  I also need information
         about  your  system:  OS  version  (DOS,  Windows 3.x,  Win32s,
         Windows 95, Windows NT, OS/2), available memory size (RAM, swap
         file),   installed   drivers,  network,   concurrently  running
         programs  (e.g. debuggers,  ...), so  everything that  could be
         important to help me searching the bug and solving the problem.

         NOTE:  AS DESCRIBED IN THE "DISCLAIMER  OF WARRANTY" SECTION OF
         THE  SXT DOCUMENTATION (SXT.DOC) THIS  SOFTWARE IS PROVIDED "AS
         IS"  AND  WITHOUT  WARRANTY OF  ANY  KIND.  THEREFORE  THERE IS
         ABSOLUTELY NO GUARANTEE OR LIABILITY THAT A BUG WILL BE FIXED.

         [... it's not a bug, it's a feature!]



         GENERAL PROTECTION FAULT WITH SXTWIN PROGRAMS
         It has  been reported that SXTWIN programs sometimes crash with
         a general protection fault (GPF) when the Borland IDE is run in
         a  Windows DOS-box at the same time.  This may happen also with
         other programs  running in a DOS-box but the Borland IDE is the
         only reported until now.
         REASON:  This  is  probably  a  problem  with  limited  Windows
         resources (memory, device contexts, file handles). There may be
         a conflict with the limited number of only 5 (!) windows device
         contexts  which  are necessary  to  access the  screen  from an
         application for writing output. Probably the IDE takes a lot of
         the resources especially if many windows are opened.
         WORKAROUND: None






                                        1



         SXT COMMAND LINE VERSIONS SOMETIMES CRASH IN WINDOWS DOS-BOX
         It  has  been  reported by  users  that  under  certain unknown
         circumstances  the   SXT  command  line  programs  hang  during
         execution in a Windows DOS-box.
         REASON: Unknown
         WORKAROUND: None


         PROBLEMS  WITH CHANGING DRIVE AND /  OR DIRECTORY FROM SXTWIN32
         PROGRAMS
         It  has been reported  that on  some systems  the Win32s SXTWIN
         programs cannot change directory and drive from within the file
         (and  other) dialog boxes.  On some systems  changes to network
         (e.g. NFS) drives were not possible while changes between local
         drives  work  well. Also  the  behaviour of  the  same SXTWIN32
         program version  was different on the various Win32s subsystems
         it  was  used  (v1.15a,  v1.20,  v1.25,  v1.30a,  v1.30c).  For
         example,  while   all  things  are  working  well  with  v1.15a
         (including  access of  network drives), it  does not  work with
         v1.20  installed  on  the  same  system.  The  16  bit  Windows
         versions, however, seem to have no such problems.
         REASON:   Unknown.  It  is  probably   related  to  the  Win32s
         subsystems  and/or   the  (more  or  less)  compatible  32  bit
         libraries.  There may also be  changes in the  behaviour on the
         different language versions of Win32s.
         WORKAROUND: None


         RECURSIVE  DIRECTORY SEARCH  DOES NOT WORK  WITH SXTWIN  16 BIT
         WINDOWS VERSIONS RUNNING ON WINDOWS NT OR WINDOWS 95
         The  recursive directory  search for  source files  (e.g. +*.c)
         does  not  work with  the  SXTWIN 16  bit  versions  running on
         Windows  NT   or  Windows  95.  It  seems  that  there  are  no
         subdirectories found.  The 16 bit real mode versions running in
         a DOS-box, however, work correctly.
         REASON: Unknown.
         WORKAROUND: None


         FATAL ERRORS DURING C/C++ PREPROCESSING WITH SOURCE FILES WHICH
         COMPILE WITHOUT ERRORS
         If reasons  like missing include paths (-I), (un-) defines (-U,
         -D) or  file open/access errors have been excluded as source of
         the   errors,  there   remain  still   some  cases   where  the
         preprocessor reports 'fatal error:...'.
         REASON:  The  integrated  preprocessor (which  is  in  fact the
         oldest  part  of  CXT -  prior  to  ANSI-C)  has  problems with
         recursive expansion of macros ("rescanning") and with expansion
         of  macro parameters, especially if  the source makes extensive
         use of stringizing # or catenation ##. This is a bug in CFT and
         CST.  Unfortunately, I do currently  see no chance  to fix this
         bug,   cause  this  would  require  a   major  rewrite  of  the
         preprocessor.
         WORKAROUND: Either  use option -NOUNSAFE or, better, preprocess
         the  sources  with your  compiler specific  preprocessor  to an
         intermediate file  and analyze the resulting output. Be sure to
         enable  the insertion  of '#line ...'  directives to  get valid
         filename and line number references.

                                        2





         HTML AND RTF FILES PRODUCE ERRORS WITH NON-ANSI CHARACTERS
         In some  rare cases SXT HTML files display wrong characters and
         it is impossible to compile SXT RTF files due to fatal errors.
         REASON:  The described problems are caused by  the use of 8-bit
         characters  which are not  part of  the ANSI  character set for
         function, data type or variable names. Such characters are, for
         example, German 'Umlauts' or French 'accents'. For standardized
         languages  like  C or  C++ their  use is  usually  not allowed,
         however, lots of compiler vendors provide these extensions.
         WORKAROUND: Do not use such characters.



         Copyright (C) Juergen Mueller (J.M.) 1988-1996.
         All rights reserved world-wide.

         SXT (TM) SOFTWARE EXPLORATION TOOLS
         SXTWIN (TM) SOFTWARE EXPLORATION TOOLS for Windows







































                                        3